Follow the engine chain to the backdrop pass, and 0.8.2 - #156
Merged
Conversation
anyrender f1c53ba renders a backdrop from inside the layers a page opens instead of declining it, so glass reaches the CPU paths: headless captures and the debug controller's screenshots. ps-blitz a81bea5 carries that plus a screenshot painted at the document's own scale, and tauri-runtime-blitz 070ab3a follows both. Every manifest moves together, which `scripts/check-one-rev-per-git-source.sh` confirms. Two revisions of one git source put two copies of a crate in the graph and surface as unrelated `PaintScene` traits rather than as a version error.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repin and version bump.
ps-anyrenderto f1c53ba: vello_cpu renders a backdrop from inside the layers a page opens instead of declining it, sobackdrop-filterworks in the CPU paths as well as on the GPU.ps-blitzto a81bea5: the above, plus a CPU screenshot painted at the document's own scale rather than a hardcoded 1.0.tauri-runtime-blitzto 070ab3a: follows both.Every manifest in the workspace moves together;
scripts/check-one-rev-per-git-source.shpasses.Verified:
cargo check -p az-gui --features blitz-inspectorclean,cargo fmt --all -- --checkclean, 249 tests pass.I also audited every local branch against master by tree rather than by commit, since rebase-merges make
git cherrylie here. All seven (chore/release-0.8.1,docs/glass-pass-measurements,feat/ui-2.2-port,fix/build-rs-formatting,fix/experimental-boot-crash,fix/transcript-tail-persistence,wip/local-save-20260815) differ from master by zero bytes on their own files. Nothing is outstanding and nothing needs a PR.